feat: add AF_VSOCK listener - #50
Closed
cablehead wants to merge 1 commit into
Closed
Conversation
cablehead
force-pushed
the
feat/vsock-listener
branch
from
August 7, 2026 15:03
ca17fd6 to
b28a5e8
Compare
Owner
Author
|
I no longer have a personal need for this. If you do, swing by https://discord.com/invite/YNbScHBHrh and have a chat! It should be easy to add. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a third transport alongside TCP and Unix domain sockets, so a Cloud Hypervisor / libkrun guest can expose http-nu over AF_VSOCK and the host can bridge it to a unix socket.
Usage
http-nu vsock://80 serve.nu(also acceptsvsock://<cid>:<port>; always bindsVMADDR_CID_ANY)Details
vsockcargo feature (indefault);tokio-vsockis target-gated so macOS/Windows still build with the feature inert.acceptreturns no peer address, like the UDS path:remote_ip/remote_portstay absent and--trust-proxykeeps resolvingX-Forwarded-Forwithout panicking.vsock://:<port>.remote_vsock: {cid, port}metadata deferred for now.Verification
vsockfeature (code fully gated).test_bind_vsockround-trips over the host-local CID (1), no hypervisor needed.cargo clippy --all-features -D warningsclean.